…ase9-metric-gap-fill

…hase2-rpc-tracing

…-tx-tracing

…hase1c-rpc-integration

…XRPLF/rippled into pratik/otel-phase10-workload-validation

…cleaner)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…(misc-include-cleaner)

std::ranges::transform/all_of come from <algorithm>, which is already included.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…nclude-cleaner)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…hase1c-rpc-integration

…hase2-rpc-tracing

…-tx-tracing

# Conflicts:
#	include/xrpl/telemetry/SpanGuard.h

…ase6-statsd

…consensus-tracing

…phase5-docs-deployment

Signed-off-by: Pratik Mankawde <3397372+pratikmankawde@users.noreply.github.com>

- OTelCollector::formatName made static (no member state); braces added;
  <cctype> added for std::tolower.
- Telemetry.cpp getMeter(): braces around single-statement if.
- GetMeter.cpp: drop unused <opentelemetry/metrics/meter.h> and
  sync_instruments.h; add <xrpl/beast/utility/Journal.h> and <memory>;
  make sdkProvider const.
- ValidationTracker.h: add <cstddef> for std::size_t.
- detail/ValidationTracker.cpp: use std::views::reverse range-based loop;
  add <ranges>.
- test ValidationTracker.cpp: use auto for cast result.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…se8-log-correlation

…ase9-metric-gap-fill

…ase10-workload-validation

…ve-metrics

…ervice' to 'Service Name'

Continuation of the same rename applied on phase-6-statsd (commit
91c6582): 5 more dashboards introduced on phase-7 (formerly the
system-* set, renamed to bare names by 2c590a4) still carried the
older 'Service' UI label. Aligning them with the rest.

Same reasoning as the phase-6 commit: the underlying Prometheus label
is `service_name`, and the UI label 'Service' misled users into typing
`service=xrpld` in Grafana Metrics Drilldown.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…se8-log-correlation

…hase2-rpc-tracing

# Conflicts:
#	.github/scripts/levelization/results/loops.txt

…-tx-tracing

…consensus-tracing

…phase5-docs-deployment

# Conflicts:
#	include/xrpl/telemetry/Telemetry.h

…ase6-statsd

…ve-metrics

# Conflicts:
#	include/xrpl/telemetry/Telemetry.h
#	src/libxrpl/telemetry/TelemetryConfig.cpp

Convert leading /// blocks in these 9 phase3-originating files to house
style /** */ (using the updated fix_doxy.py that now handles /// ->
block conversion). Comment-only: code is byte-identical.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

… refresh levelization

Convert leading /// blocks to house-style /** */ across the telemetry
files carried on this branch (using the updated fix_doxy.py). Also
regenerate levelization results. Comment-only: code is byte-identical.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Convert leading /// blocks in LedgerSpanNames.h and PeerSpanNames.h to
house-style /** */. Comment-only: code is byte-identical.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…consensus-tracing

# Conflicts:
#	include/xrpl/telemetry/TraceContextPropagator.h
#	src/xrpld/telemetry/PropagationHelpers.h

…phase5-docs-deployment

# Conflicts:
#	src/xrpld/telemetry/PropagationHelpers.h

…ase6-statsd

…ve-metrics

…se8-log-correlation

xrpl_branch and xrpl_node_role are collector/infra-injected resource
labels used by perf-iac dashboards to identify the build under test and
its role in the perf cluster. They have no L1 span-attribute source or
L6 native-metric-label source (like the existing job/instance/job_type
builtins), so Rule D flagged them across every perf-iac dashboard.
Register them in the builtins set, matching the existing pattern for
infra-level dashboard labels. Add test coverage.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…ing Rule D"

This reverts commit 48747ba.

…g Rule D

xrpl_branch and xrpl_node_role are stamped by the perf-iac harness --
infrastructure outside this repo's OTel code -- so they have no L1
(*SpanNames.h), L2 (collector config), or L6 (MetricsRegistry.cpp) source
Rule D can derive them from. Unlike the generic builtins set (Prometheus/
Grafana mechanics every OTel setup has), these are repo-specific and
narrow, so they get their own EXTERNAL_INFRA_LABELS constant: a visible,
documented, deliberately narrow exception to the 'no hardcoded allowlist'
design principle, not a silent workaround. Add test coverage.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…hase2-rpc-tracing

…-tx-tracing

…consensus-tracing

…phase5-docs-deployment

…ase6-statsd

…ve-metrics

…se8-log-correlation

…ase9-metric-gap-fill

# Conflicts:
#	src/xrpld/telemetry/ValidationTracker.h

…ase9-metric-gap-fill

…ase10-workload-validation

# Conflicts:
#	src/xrpld/telemetry/MetricsRegistry.h
#	src/xrpld/telemetry/ValidationTracker.h

…h comments

An earlier Doxygen-style normalization pass on this file introduced a
stray xrpld_ prefix into 5 comment references to the validation
counters/gauge. The actual instrument names registered in
MetricsRegistry.cpp have no such prefix (validation_agreements_total,
validation_missed_total, validation_agreement). Comment-only fix.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…ase10-workload-validation